SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Liquid computing</title>

</head>

Liquid computing

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">This article is about the computing concept. For the company, see <a href="Liquid_Computing" title="Liquid Computing">Liquid Computing</a>.</div>

Liquid computing refers to a style of workflow interaction of applications and computing services across multiple devices, such as computers, smartphones, and tablets. The term was coined in July 2014 by <a href="InfoWorld" title="InfoWorld">InfoWorld</a>,<a href="#cite_note-1">[1]</a><a href="#cite_note-2">[2]</a><a href="#cite_note-3">[3]</a><a href="#cite_note-4">[4]</a><a href="#cite_note-5">[5]</a><a href="#cite_note-6">[6]</a> but the underlying concepts have long existed in <a href="Computer_science" title="Computer science">computer science</a>, such as in the notions of <a href="Pervasive_computing" class="mw-redirect" title="Pervasive computing">pervasive computing</a> and <a href="Ubiquitous_computing" title="Ubiquitous computing">ubiquitous computing</a>. The key differentiator for liquid computing over other related notions is that of being focused on the movement among devices of a workflow involving people.

In a liquid computing approach, a person might work on a task on one device, then go to another device that detects the task in progress at the first device and offer to take over that task. For example, you might begin composing an email on a smartphone and when you come near your computer, its mail software detects the in-progress email and lets you continue to work on it on the computer. The data involved, including its current state, flows from one device to another (more accurately, from an application on a device to an application on another device), thus the term "liquid computing."

An example of this approach is <a href="Apple_Inc." title="Apple Inc.">Apple</a>'s <a href="Handoff_(Continuity)" class="mw-redirect" title="Handoff (Continuity)">Handoff (Continuity)</a> service in <a href="IOS_8" title="IOS 8">iOS 8</a> and <a href="OS_X_Yosemite" title="OS X Yosemite">OS X Yosemite</a> (the feature is available only for compatible devices, such as iOS devices with a Lightning port and 2012-or-later Mac models that support <a href="Bluetooth_Low_Energy" title="Bluetooth Low Energy">Bluetooth Low Energy</a> and <a href="Wi-Fi_Direct" title="Wi-Fi Direct">Wi-Fi Direct</a>).<a href="#cite_note-7">[7]</a><a href="#cite_note-8">[8]</a>

<a href="Google" title="Google">Google</a> has announced a similar approach for applications in its <a href="Android_Lollipop" title="Android Lollipop">Android Lollipop</a> operating system and its <a href="ChromeOS" title="ChromeOS">ChromeOS</a> operating system to interact with each other in a manner similar to Handoff.<a href="#cite_note-9">[9]</a>

A limitation of current liquid computing implementations is that they are confined to specific vendors' platforms, such as within Apple's iOS and OS X pair or within Google's Android and ChromeOS pair. That means workflows can't flow across different vendors' devices, such as from an Apple <a href="IPad" title="IPad">iPad</a> to a Microsoft Windows <a href="Personal_computer" title="Personal computer">PC</a>. That is not a technical limitation of the liquid computing concept but a vendor decision to encourage adoption of its product ecosystem. Both Apple and Google, for example, make liquid computing capabilities available to developers through a set of <a href="API" title="API">APIs</a> that theoretically could be made available to competing platforms, but currently are not. To address this problem, the liquid computing concept can be applied to Web applications running across different Web-enabled devices.<a href="#cite_note-10">[10]</a>

<div class="mw-heading mw-heading2"><h2 id="Liquidity_as_a_Quality_Attribute">Liquidity as a Quality Attribute</h2></div>

More in general, liquid software features flexible redeployment in response to changes to the software and to its execution environment.<a href="#cite_note-11">[11]</a> As the software is updated, the new version is seamlessly redeployed, replacing the previous one without any user disruption. As the devices on which it runs change (as in the above user workflow scenario), the software smoothly follows the user attention focus from one device to the next. Overall, within the <a href="List_of_system_quality_attributes" title="List of system quality attributes">List of system quality attributes</a>, liquidity can be defined as the combination of deployability with flexibility.

<div class="mw-heading mw-heading2"><h2 id="Related_technologies">Related technologies</h2></div>

Several operating systems — Apple's iOS and OS X<a href="#cite_note-12">[12]</a> and Microsoft's <a href="Windows_8" title="Windows 8">Windows 8</a><a href="#cite_note-13">[13]</a> — can sync settings across multiple devices, as can the <a href="Google_Chrome" title="Google Chrome">Google Chrome</a> browser and <a href="Apple_Safari" class="mw-redirect" title="Apple Safari">Apple Safari</a> browser. The cross-device interaction concept is similar to liquid computing, but lacks the workflow characteristic of liquid computing.

Another related concept involves transferring a service from one device to another, such as sending a phone call or text message from a phone to a computer. Apple does not include this capability (available in OS X Yosemite and iOS 8) in its definition of Handoff, but instead assigns this feature to its set of services called Continuity,<a href="#cite_note-14">[14]</a> which includes Handoff. <a href="BlackBerry" title="BlackBerry">BlackBerry</a> has a similar capability called Blend available for its smartphones to send calls or texts to OS X Macs and Windows PCs. These transfer services are similar to phone or email forwarding in that the communications is forwarded to another available device (usually via a Wi-Fi connection), and there's no interaction with the data itself as there is in liquid computing. Also, liquid computing allows multiple handoffs during the workflow, whereas communications transfers do not.

Likewise, the <a href="Internet_of_things" title="Internet of things">Internet of things</a> notion is similar to liquid computing in that it involves direct communication among devices for a computing-oriented purpose, such as analyzing a person's level of physical activity, tracking users in a shopping mall to determine coupon offers, or correlating traffic conditions and flow to recommend alternative routes. Data flows among devices or to a central application hosted on a back-end server, but at most only part of the workflow involves a person, not the entire chain of activity.

The various kinds of computer-to-computer interactions and human-computer interactions that include liquid computing are not exclusive to each other; the various type of interactions can be combined.<a href="#cite_note-15">[15]</a>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFGruman" class="citation web cs1">Gruman, Galen. <a rel="nofollow" class="external text" href="http://www.infoworld.com/article/2608440/ios/article.html">"Welcome to the next tech revolution: Liquid computing"</a>. infoworld.com. IDG. Retrieved 15 February 2015.</cite>

</li>

<li id="cite_note-2"><a href="#cite_ref-2">^</a> <cite id="CITEREFBridgwater" class="citation web cs1">Bridgwater, Adrian. <a rel="nofollow" class="external text" href="http://www.computerweekly.com/blogs/cwdn/2014/07/what-is-liquid-computing.html">"What is liquid computing?"</a>. computerweekly.com. TechTarget. Retrieved 15 February 2015.</cite>

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.pcmag.com/encyclopedia/term/66841/liquid-computing">"Definition of 'liquid computing'"</a>. pcmag.com. Computer Language Co. Retrieved 20 February 2015.</cite>

</li>

<li id="cite_note-4"><a href="#cite_ref-4">^</a> <cite id="CITEREFRice" class="citation web cs1">Rice, Sam. <a rel="nofollow" class="external text" href="http://www.applauseit.co.uk/blog/liquid-computing/">"Liquid Computing"</a>. applauseit.co.uk. ApplauseIT. Retrieved 20 February 2015.</cite>

</li>

<li id="cite_note-5"><a href="#cite_ref-5">^</a> <cite id="CITEREFJames" class="citation web cs1">James, Howard. <a rel="nofollow" class="external text" href="https://archive.today/20150309130752/http://www.marketsmagazine.net/liquid-computing-the-next-big-thing-in-it/">"Liquid computing: The next big thing in IT?"</a>. marketsmagazine.net. Markets Magazine. Archived from <a rel="nofollow" class="external text" href="http://www.marketsmagazine.net/liquid-computing-the-next-big-thing-in-it/">the original</a> on 9 March 2015. Retrieved 20 February 2015.</cite>

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> <cite id="CITEREFRege" class="citation web cs1">Rege, Ojas. <a rel="nofollow" class="external text" href="https://www.mobileiron.com/en/smartwork-blog/three-questions-enterprises-should-ask-about-ios-8">"Three Questions Enterprises Should Ask About iOS 8"</a>. mobileiron.com. MobileIron. Retrieved 20 February 2015.</cite>

</li>

<li id="cite_note-7"><a href="#cite_ref-7">^</a> <cite id="CITEREFGruman" class="citation web cs1">Gruman, Galen. <a rel="nofollow" class="external text" href="http://www.infoworld.com/article/2691101/ios/apples-handoff-what-works-and-what-doesnt.html">"Apple's Handoff: What works, and what doesn't"</a>. infoworld.com. IDG. Retrieved 15 February 2015.</cite>

</li>

<li id="cite_note-8"><a href="#cite_ref-8">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/Handoff/HandoffFundamentals/HandoffFundamentals.html">"About Handoff"</a>. developer.apple.com. Apple. Retrieved 15 February 2015.</cite>

</li>

<li id="cite_note-9"><a href="#cite_ref-9">^</a> <cite id="CITEREFGoode" class="citation web cs1">Goode, Lauren. <a rel="nofollow" class="external text" href="http://recode.net/2014/06/25/some-google-android-apps-will-run-on-chromebooks/">"Some Google Android Apps Will Run on Chromebooks"</a>. recode.net. Revere Digital.</cite>

</li>

<li id="cite_note-10"><a href="#cite_ref-10">^</a> <cite id="CITEREFMikkonenSystaPautasso" class="citation web cs1">Mikkonen, Tommi; Systa, Kari; Pautasso, Cesare. <a rel="nofollow" class="external text" href="http://design.inf.usi.ch/publications/2015/icwe/liquid-web-app/">"Towards Liquid Web Applications (ICWE2015)"</a>. liquid.inf.usi.ch/. Springer.</cite>

</li>

<li id="cite_note-11"><a href="#cite_ref-11">^</a> <cite id="CITEREFPautasso" class="citation web cs1">Pautasso, Cesare. <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/10234252">"A Brief History of Liquid Software (iEDGE)"</a>. IEEE.</cite>

</li>

<li id="cite_note-12"><a href="#cite_ref-12">^</a> <cite id="CITEREFBecker" class="citation web cs1">Becker, Hannah. <a rel="nofollow" class="external text" href="http://www.technologyguide.com/feature/syncing-between-ios-7-and-os-x-mavericks/">"How To Sync Apple iOS 7 and OS X Mavericks"</a>. technologyguide.com. TechTarget. Retrieved 15 February 2015.</cite>

</li>

<li id="cite_note-13"><a href="#cite_ref-13">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://windows.microsoft.com/en-us/windows-8/sync-settings-pcs">"Sync settings between PCs with OneDrive"</a>. microsoft.com. Microsoft. Retrieved 15 February 2015.</cite>

</li>

<li id="cite_note-14"><a href="#cite_ref-14">^</a> <cite id="CITEREFSpencer" class="citation web cs1">Spencer, Graham. <a rel="nofollow" class="external text" href="http://www.macstories.net/tutorials/os-x-yosemite-ios-8-continuity-explained-handoff-instant-hotspot-sms-phone-relay/">"OS X Yosemite & iOS 8 Continuity Explained: Handoff, Instant Hotspot, SMS & Phone Relay"</a>. macstories.com. MacStories. Retrieved 15 February 2015.</cite>

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> <cite id="CITEREFGruman" class="citation web cs1">Gruman, Galen. <a rel="nofollow" class="external text" href="http://www.infoworld.com/article/2855211/internet-of-things/the-power-of-2-liquid-computing-plus-the-internet-of-things.html">"The power of 2: Liquid computing plus the Internet of things"</a>. infoworld.com. IDG. Retrieved 15 February 2015.</cite>

</li>

</ol></div></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-04-11" href="https://en.wikipedia.org/wiki/?title=Liquid_computing&oldid=1285054166">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>